Custom Wiegand Formats

Introduction

The Doors.NET software has the 26-bit Wiegand card format defined and added by default. This format has 1 parity bit, 8 bits for facility code, 16 bits for the card ID and a trailing parity bit. However, also, the NXT and Keri MS formats are added by default, but there are many other different Wiegand formats that can be used - we are compatible with many reader technologies and Wiegand formats.

Standard Wiegand Format

• 26-bit Wiegand facility codes range from 0 - 255.
• 26-bit Wiegand Card ID range from 0 - 65,535.

Custom Wiegand Formats

Custom Wiegand formats are often more than 26-bit (allowing for more unique card numbers) and have varying complexity, parity checking and fields lengths, i.e for the facility code and card ID. However, most custom Wiegand formats used in access control systems will be less than 37-bit.

There are many non-standard Wiegand formats which have already been added to the Doors.NET custom format library, but it is also possible to add your own custom format to Doors.NET. Adding a custom Wiegand format is explained in section 5

2.0 Important Notes

1. NXT Standard controllers support up to 64-bit Wiegand data
2. NXT Mercury Powered (MSC) controllers support up to 126-bit Wiegand data
3. PXL controllers support up to 31-bit Wiegand
4. Any crendetials that are more than 26-bit MUST be presentation enrolled. You can only block enroll the 26-bit Wiegand credentials.

5. Because Credential Types is a licensed feature it needs to be enabled. You can check it is enabled in the License Manager, click the Windows Start menu >> All Programs >> Doors.NET >> License Manager. When the License Manager opens click on the License tab. Scroll down and you will see Credential Types within the 'Options' section, verify this is set to True.
   
   

3.0 Custom Wiegand Format Examples

4.0 How to Add a Custom Wiegand Format

A custom format must be added to the credential types library if it does not already exist. Up to 8 different custom formats can be used concurrently with the MSC or SCP controller types. If you did not purchase the custom formatted cards from Keri Systems you will need to contact the supplier for details about how the Wiegand data is formatted on the card.

4.1 Define the Bit Pattern

1. Within Doors.NET. Go to Setup >> Credential Types.
2. The Credential Types screen will open up on the active formats tab.
3. Click the Wiegand Library tab.
   
   
   
   
4. The list of available formats is shown on the left. Verify that the format of your cards is not already in the list.
5. Click the ADD FORMAT button.
6. Select the New Wiegand Format entry at the bottom of the list.
7. Give the new format a description.
8. Enter the total number of bits.
9. Enter the total length of the facility code.
10. Enter the start bit for the facility code.
11. Enter the card number length.
12. Enter the start bit for the card number.
13. Enter the number of bits for even parity.
14. Enter the even parity start bit.
15. Enter the number of bits for odd parity.
16. Enter the odd parity start bit.
17. The issue code fields are usually left blank.

4.2 Bit Pattern Options

• Step Parity Calculations by 2-bits - Moves the positions of the parity bits.

• The Suppress Facility Code Checking check box configures the readers to ignore the facility code of presented cards.

• The Corporate Card Calculations check box changes how the card number is computed for this format. The card number is offset by the multiplying the facility code by the offset number.

• The two 37 bit options are for a specific Motorola format.

• The 64 bit with Bistatic Parity are for some of the Desfire formats. However, not all Desfire formats use that parity.

• The 48-bit FASCN is the TWIC format the TSA uses; Transportation Worker Identification Credential.

• The Reverse bit pattern before processing flips the bits in reverse. Some formats are setup in this way.